Skip to content

Conversation

SangJunBak
Copy link
Contributor

Motivation

Tips for reviewer

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

- Created a factory function to create Scenarios
- For the platform-checks CLI, converted scenario argument to regex search to capture multiple versions
@SangJunBak SangJunBak changed the title Jun/multi version upgrade test to latest version Multi version upgrade tests to latest version Oct 14, 2025
@SangJunBak SangJunBak force-pushed the jun/multi-version-upgrade-test-to-latest-version branch from b5aee52 to d1f1911 Compare October 14, 2025 20:48
- Add pipeline to CI
- Enhanced error handling by wrapping scenario execution in try-except blocks to capture and print exceptions during runtime
- Add debug log filter
- Add teardown for each scenario run
- Allow failures to not end the pipeline
@SangJunBak SangJunBak force-pushed the jun/multi-version-upgrade-test-to-latest-version branch 2 times, most recently from 14bca33 to df1d60a Compare October 15, 2025 02:04
- Targets only minor versions rather than all patch releases
- Ran than all checks, runs against CreateCluster check
- Adds additional logging for pipeline
- Hard code timeout of 60 seconds
@SangJunBak SangJunBak force-pushed the jun/multi-version-upgrade-test-to-latest-version branch 2 times, most recently from 7743484 to ad4f721 Compare October 15, 2025 18:15
- Increased timeout for 0dt upgrade checks from 120 to 240 minutes
- Updated minimum version requirement for zero downtime scenarios to v0.126.0 since that's the earliest version can upgrade successfully
- Run for all checks instead of one
- Remove skipping of healthchecks
@SangJunBak SangJunBak force-pushed the jun/multi-version-upgrade-test-to-latest-version branch from ad4f721 to 17c482d Compare October 16, 2025 13:31
- Added execution mode option to the CI pipeline for one-at-a-time execution.
- Introduced a fast teardown function to streamline resource cleanup during tests.
- Don't stop process on failure of a check
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant